Policy control architecture for blade servers upon inserting into server chassis

ABSTRACT

A system for implementing and controlling a plurality of server-specific policies for a plurality of servers using a management module in communication with the plurality of servers is provided. A policy controller module is operational on the management module. The policy controller module is adapted for defining a first policy of a plurality of policies for each of the plurality of servers, managing a plurality of rules relevant to an execution of the first policy, and coordinating the execution of the first policy with an execution of a second policy of the plurality of policies.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. Non-Provisional application Ser.Nos. 12/112,174 and 12/112,195 filed concurrently herewith andincorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates in general to computers, and moreparticularly to a policy control architecture for a plurality ofservers.

2. Description of the Related Art

Multiple blade servers are computers that consolidate high-densityserver boards (blades) in a single blade chassis (server blade chassis).Typically, a server blade chassis accommodates multiple hot-swappableserver blades. The operations of the blades may be supervised bymanagement functionality sometimes embodied as a “management module.”Management modules may include or may be associated with a processor forcontrolling input/output functions and interfacing with a network (suchas the Internet or a Local Area Network).

Server blade chassis environments, housing a number of individual serverblades, can provide flexibility in configuration and implementation ofcomputing functionality for a user in a variety of settings, includingbusiness, government, and elsewhere. Such computing functionality mayinclude processing functionality and storage functionality. As computingneeds of a particular user may evolve over time, individual serverblades may be configured and implemented to address these needs. Forexample, individual server blades may be implemented as storage bladesor processor blades depending on associated hardware as needed for aparticular application.

SUMMARY OF THE INVENTION

While management modules provide some existing control, interface, andprocessing functionality, currently there is an inability to use themanagement module to provide a collective, policy-based managementscheme for a variety of individual servers. For example, there iscurrently no centralized method to configure and manage the functions ofa particular server's basic input output system (BIOS) per a specificpolicy within the management module. In another example, if theoperating system of an application server resides on a particular volume(either on an associated storage blade or elsewhere), and theapplication server suffers from a hardware failure, the entire systemfails. The user must then manually remap another server to point to thevolume containing the operating system.

In light of the foregoing, a need exists for a method, system, andcomputer program product for implementing and controlling a plurality ofserver-specific policies for a plurality of servers. Accordingly, in oneembodiment, a method for implementing and controlling a plurality ofserver-specific policies for a plurality of servers by a managementmodule in communication with the plurality of servers is provided. Afirst policy of a plurality of policies is defined for each of theplurality of servers. A plurality of rules is managed. The rules arerelevant to an execution of the first policy. The execution of the firstpolicy is coordinated with an execution of a second policy of theplurality of policies.

In another embodiment, again by way of example only, a system forimplementing and controlling a plurality of server-specific policies fora plurality of servers using a management module in communication withthe plurality of servers is provided. A policy controller module isoperational on the management module. The policy controller module isadapted for defining a first policy of a plurality of policies for eachof the plurality of servers, managing a plurality of rules relevant toan execution of the first policy, and coordinating the execution of thefirst policy with an execution of a second policy of the plurality ofpolicies.

In another embodiment, again by way of example only, a computer programproduct for implementing and controlling a plurality of server-specificpolicies for a plurality of servers by a management module incommunication with the plurality of servers is provided. The computerprogram product comprising a computer-readable storage medium havingcomputer-readable program code portions stored therein. Thecomputer-readable program code portions comprise a first executableportion for defining a first policy of a plurality of policies for eachof the plurality of servers, a second executable portion for managing aplurality of rules relevant to an execution of the first policy, and athird executable portion for coordinating the execution of the firstpolicy with an execution of a second policy of the plurality ofpolicies.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readilyunderstood, a more particular description of the invention brieflydescribed above will be rendered by reference to specific embodimentsthat are illustrated in the appended drawings. Understanding that thesedrawings depict only typical embodiments of the invention and are nottherefore to be considered to be limiting of its scope, the inventionwill be described and explained with additional specificity and detailthrough the use of the accompanying drawings, in which:

FIG. 1 depicts an exemplary server blade chassis incorporating anadvanced management module (AMM) in which aspects of the claimed subjectmatter may be implemented; and

FIG. 2 is an block diagram of an exemplary advanced management module,including a policy controller module and associated sub-modules;

FIG. 3 is a flow chart diagram of an exemplary method of implementingand controlling a plurality of blade-specific policies within a serverblade chassis;

FIG. 4 is a flow chart diagram of an exemplary pre-insertion applicationroutine for an exemplary slot policy;

FIG. 5 is a flow chart diagram of an exemplary blade insertion routinefor an exemplary slot policy;

FIG. 6 is a flow chart diagram of an exemplary blade insertion routinefor an exemplary blade policy;

FIG. 7 is a flow chart diagram of an exemplary blade removal routine foran exemplary blade policy;

FIG. 8 is a flow chart diagram of an exemplary power-on routine for anexemplary blade sparing policy;

FIG. 9 is a flow chart diagram of an exemplary blade-insertion routinefor an exemplary blade sparing policy;

FIG. 10 is a flow chart diagram of an exemplary blade failure routinefor an exemplary blade sparing policy;

FIG. 11 is a flow chart diagram of an exemplary spare blade removalroutine for an exemplary blade sparing policy;

FIG. 12 is a flow chart diagram of an exemplary power-on routine for anexemplary volume sparing policy; and

FIG. 13 is a flow chart diagram of an exemplary volume failure routinefor an exemplary volume sparing policy.

DETAILED DESCRIPTION OF THE DRAWINGS

The present description and claimed subject matter describe exemplarysystem, method, and computer program product embodiments forimplementing a policy-based management scheme using an advancedmanagement module (AMM) within a blade server chassis. These embodimentsuse components of the multi-blade server, such as the aforementionedadvanced management module, to centrally configure and manage policiesand rules related to the execution of those policies. Further, thecomponents may then execute and coordinate the execution of multiplepolicies in view of additional policies and rules. The components may beremotely accessible and configurable by use of software such as a webapplication over a network. Such embodiments provide for remote,centralized management and control of each blade in the chassis throughan interface.

FIG. 1 is an exemplary block diagram of a server blade chassis 200 a.For the sake of clarity, only three server blades 204 a,b,n aredepicted. However, in one embodiment, server blade chassis 200 a has amidplane 206 capable of connecting fourteen or more server blades 204.

Server blade chassis 200 a has one or more advanced management modules202. In the depicted embodiment, server blade chassis 200 a has aprimary advanced management module 202 a and a back-up advancedmanagement module 202 b. Each advanced management module 202 is capableof managing multiple server blades 204. During normal operations, one ofthe local advanced management modules 202 a or 202 b are coupled toserver blades 204 a-n via a Local Area Network (LAN) 240 a, a midplane206, and a plurality of Baseboard Management Controllers (BMCs) 208(each server blade 204 having a BMC 208) to form an in-band managementpathway. LAN 240 and BMC 208 are discussed in further detail below.

Midplane 206 is a backplane, mounted in the middle of server bladechassis 200 a, that contains circuitry and sockets 222 into whichadditional electronic devices or cards, including server blades 204 maybe inserted. Midplane 206 contains at least one bus for secure in-bandinternal communication between management module 202 and server blades204 a-n, as well as between and among server blades 204 a-n themselves,via respective BMCs 208 a-n.

When a server blade 204 is inserted into a specific socket 222, aphysical address is established for that server blade 204. For example,consider server blade 204 a being inserted into socket 222 a. A controllogic 224 a detects the presence of server blade 204 a in socket 222 a.Logic 224 a may comport with the Electronics Industry Association (EIA)RS485 Standard for data communication. In other embodiments, Logic 224 amay be compliant with the Phillips' Inter-IC (Inter-Integrated Circuit)standard (incorporated by reference in its entirety herein and commonlyreferred to as “I²C”), or with an Ethernet network standard. Logic 224a, operating in conjunction with management module 202, assigns aphysical address on a bus in midplane 206 to server blade 204 a whenserver blade 204 a is inserted into socket 222 a. Each server blade 204may be associated with a unique logic 224 that is connected to midplane206 as depicted in FIG. 2 a. Alternatively, all server blades 204 mayuse a single logic 224.

Each server blade 204 may have a unique Internet Protocol (IP) addresson midplane 206. That is, midplane 206 may support intercommunicationusing IP addressing protocol, in which each device connected or coupledto midplane 206 contains an IP address assigned by logic (not shown)that is either within or outside server blade chassis 200. For example,a Dynamic Host Configuration Protocol (DHCP) server may be used toassign an IP address to server blade 204 a. Communication with serverblade 204 a is thereafter via a Network Interface Card (NIC) 226 a thatis associated with server blade 204 a. The communication pathway usingswitches 242 a and NICs 226 may be referred to as an out-of-band (OOB)network.

Each server blade 204 may have at least one central processing unit(CPU) 212, and a non-volatile memory (NVM) 214. NVM 214 is a Flash ReadOnly Memory (“Flash ROM” or “Flash Memory”) that can be erased andreprogrammed in units of memory referred to as “blocks.” NVM 214 mayalso include non-volatile Electrically Erasable Programmable Read OnlyMemory (EEPROM) that is similar to Flash Memory, except that EEPROM iserased and rewritten at the byte level and is usually smaller incapacity.

When a server blade 204 is shipped from a manufacturer, the NVM 214 maybe pre-burned with firmware, including a BIOS as well as software formonitoring the server blade 204. Such monitoring may include controllingDirect Access Storage Devices (DASD's), monitoring and controllingvoltages throughout the system, determining the power-on status of theserver blade 204, requesting access to a shared keyboard, video, mouse,Compact Disk-Read Only Memory (CD-ROM) and/or floppy disk drives, aswell as monitoring the Operating System (OS) running on the server blade204.

As previously described, various related functionality in addition totraditional BIOS functionality may be associated with each blade 204a-n. This includes Extensible Firmware Interface (EFI) and (FirmwareSystem Processor) FSP functionality. EFI is an emerging technology thatprovides a buffer between the operating system (OS) and the BIOS. Forexample, in a boot operation, the BIOS turns directly to EFI for pre-OSfunctions to be executed. EFI provides functionality a level ofabstraction apart from the computer hardware. EFI may run an embeddedReal Time Operating System (RTOS) that provides programmers withadditional power and control over pre-OS functions. A FSP may containsystem firmware and system code. As a result, FSP functionality relatesto system functionality. For purposes of the instant description andclaimed subject matter, reference to the term “BIOS” incorporates EFIand FSP functionality, as such functionality may be also centrallycontrolled and configurable using methodologies described herein.

Management modules 202 are capable of detecting the presence, quantity,type and revision level of each server blade 204, power module 210, andmidplane 206 in the system. Management modules 202 may also directlycontrol the operation of each server blade 204 and the power module 210,and may directly (without using the BIOS in the server blades 204) orindirectly (using the BIOS) control the operation of cooling fans 215and other chassis 200 a components.

Each server blade 204 has a Baseboard Management Controller (BMC) 208that provides local supervisory control of the server blade 204 to whichthe BMC 208 is associated. Each BMC 208 is able to communicate with alocal management module 202 by either using communication path 240 a(in-band network) or alternatively by using switches 242 a and NICs 226(out-of-band network). The local management modules 202 a, 202 b mayutilize a variety of communications paths 240 a, such as an RS485 path240 a, a LAN path 240 a and an I²C path 240 a to communicate with eachblade 204.

LAN 240 is an in-band network also comporting with the ElectronicsIndustry Association (EIA) RS485 Standard for data communication.Management modules 202 (either primary management module 202 a orback-up management module 202 b if management module 202 a is down)communicate via LAN 240 with BMC 208, which includes logic forcoordinating communication with server blades 204 via sockets 222. Thatis, the primary communication pathway between management module 202 andserver blades 204 is the in-band network that comprises LAN 240, sockets222, and BMC 208. The secondary communication pathway, which is used inthe present invention if all of the local management modules 202 shouldfail, is the OOB network that comprises switches 242 and NICs 226.

LAN 240 a may be configured to allow communications between serverblades 204 a-n and the management modules 202 a, 202 b relating to theremote BIOS settings and BIOS management. The blades 204 a-n mayleverage BMCs 208 a-n as proxies to communicate with the managementmodules 202 a, 202 b through the RS485 protocol. Similarly, themanagement modules may leverage BMCs 208 a-n as proxies to communicatewith the blades 204 a-n through the RS485 protocol. In an alternativeembodiment, an RS485 connection may be separately made between eachblade 204 a-n and the management modules 202 a, 202 b. Additionally,other communications protocols and paths may be utilized, such as theaforementioned I²C channel or the aforementioned TCP/IP and/or Ethernetchannel over switches 242 a.

FIG. 2 depicts an exemplary advanced management module (AMM) 202 a infurther detail, incorporating a policy controller module 250 incommunication with associated sub-modules as will be further described.Policy controller module 250 acts to define and initialize a number ofblade-specific policies for a number of blades operational on aparticular server blade chassis. A number of policies relevant todifferent aspects of operation of the various server blade devices maybe defined. The definitions may be stored by the policy controllermodule 250 and located on the policy controller module 250, on anotherportion of the AMM 202 a, or elsewhere. The policies may relate tomanagement, operation, organization, and sparing, for example. Exemplarypolicies will be further described in more detail, following.

A number of definitions and rules relevant to the execution of eachpolicy may be maintained and managed by the policy controller module250. These rules may relate to or include certain “predeterminedtrigger” mechanisms, for example, that indicate to the AMM 202 a that itis appropriate to execute a particular policy. The trigger mechanismsmay include the action of inserting a new server blade device into theserver blade chassis, or removing a server blade device from the serverblade chassis. The trigger mechanism may include a failure of a hardwarecomponent within the server blade chassis, such as a server bladefailure. As one skilled in the art will appreciate, a number of rulespertaining to a particular blade-specific policy may be maintained.

Policy controller module 250 coordinates the execution of multiplepolicies within the server blade chassis for a number of resources(e.g., storage resources) operational within the server blade chassis.For example, the policy controller module 250 may, as a result of apredetermined trigger such as a blade insertion, execute a first policy,e.g., a blade policy. An additional trigger mechanism such as a bladefailure may result in the execution of a second policy, e.g., a bladesparing policy. The policy controller module 250 may execute the secondpolicy in view of the rules of the second policy, as well as the rulesof the first policy. In this manner, a variety of policies may beconcurrently (or as the case may require, sequentially) executed on theAMM 202 a as they pertain to an individual server blade.

A number of sub-modules are shown incorporated into the exemplary AMM202 a, although the number and functionality depicted is not exclusiveand may vary depending on a particular implementation. In some cases,these sub-modules may be integrated together (physically or logically).In other cases, the sub-modules may be entitled differently, as much ofthe functionality described herein as applied to the sub-modules may beorganized in various ways. In other cases, the sub-modules may bedispersed throughout the AMM 202 a, or located elsewhere, yet remain incommunication with the policy controller module 250.

Policy controller module 250, while coordinating the execution of one ormore of the policies, may assign one or more of the definitions, rules,along with the policy itself, to a sub-module for execution. Forexample, a particular sparing policy, incorporating a number of sparingrules and definitions, may be assigned by the policy controller module250 to a sparing sub-module for execution.

The depicted sub-modules as shown in FIG. 2 include a BIOS module 252(including a remote BIOS partition 254 and a remote BIOS interface 256),an operating system repository module 258, an information manager module260, an application module 262, a configuration/reconfiguration module264 (including a configure switch module 266 and a configure storagemodule 268), a compatibility matrix module 270, and a sparing module272. The depicted sub-modules as shown are in communication with eachother, the policy controller module 250, and the AMM 202 a.

The AMM 202 a through the use of interfaces may be configured to retaina mapping of blades to BIOS settings maintained on information managermodule 260, BIOS module 252, or elsewhere. Each newly inserted blade maybe allocated a particular logical partition by BIOS module 254 for itsparticular BIOS settings. The BIOS settings may be stored in astandardized format. The AMM 202 a may be configured to provide a newblade with a default set of BIOS settings/preferences.

To implement a remote BIOS, such as a BIOS for each blade of amulti-blade server as depicted in FIG. 1, a series of BIOS settings maybe defined for each blade 204 a-n. The settings may be configured toreside on a central management device and interface of the chassis suchas an advanced management module 202 a. Each blade's individual BIOS maybe modified to always query the management module for blade-specificBIOS settings. The management module may then respond to the query withthe blade-specific BIOS settings. The blade-specific BIOS settings couldbe initially set to default settings if a particular blade has neverbeen inserted into the chassis 200 a (FIG. 1). Alternatively, if theparticular blade matches a set profile, the AMM 202 a may provide asaved set of profile-specific BIOS settings. AMM 202 a, 202 b (FIG. 1)may be configured to communicate to each server blade both internallyand externally (e.g., over an external network) via a particularchassis. In addition, the advanced management modules 202 a, 202 b maybe adapted to be remotely configurable to simplify and minimize theinteraction that the user has to have with respect to a particularserver blade.

A remote BIOS partition 254 may be created within the AMM 202 a for eachblade (e.g., blades 204 a-n) associated with the AMM 202 a. Remote BIOSsettings that are blade-specific may then reside in each remote BIOSpartition. A central logical partition interface such as remote BIOSinterface 256 may be implemented within the advanced management modules202 a, 202 b (FIG. 1) adapted to control the BIOS (including EFI and FSPfunctionality) for each blade 204 a-n. In addition, the remote biosinterface 256 may be adapted to allow a user to remotely configure andmodify settings such as the BIOS settings of a particular blade withoutthe user having to enter a menu residing on the particular blade. Eachblade 204 a-n may be configured to cache the BIOS settings for caseswhen the AMM 202 a, 202 b (FIG. 1) are not accessible.

Operating system (OS) repository module 258 may store a number ofoperating systems which are designated for each of the server blades.For example, the operating system repository module 258 may store anAdvanced Interactive Executive (AIX) operating system, as well as aWindows® based OS. In the event that an OS on boot designated volume isnot present, the OS repository module 258 may initialize the volume witha designated OS. OS repository module 258 may perform various additionalOS functionality as it pertains to a selected server blade.

Information manager module 260 may be configured to store and retrieve avariety of information relevant to a particular blade (such as mappingsrelevant to components of the particular blade), a particular policy fora selected blade, rules relevant to the execution of the policy, and thelike. During the execution of a particular policy, the informationmanager module 260 may access, retrieve, and later store theinformation, definitions, rules, etc. During the execution of aparticular policy, information manager module 260 may manage the flow ofinformation between sub-modules and to/from the policy controller module250. For example, a particular blade sparing policy may require a userinput to designate whether a selected server blade will be assigned tobe used live or as a spare. The user input may be elicited, retrieved,and stored by the information manager module 260.

Application module 262 may be employed by policy controller module 250to execute various policy-specific applications. The applications may beused during the execution of a particular policy. Policy controllermodule 250 may control the use of these applications per the executionof a particular policy for a particular server blade or at a particulartime. The applications may vary per the policy involved. For example,various applications may be used towards implementing a sparing policyfor a selected server blade, and additional applications may be usedtowards implementing a BIOS policy for an additional server blade.

Configuration/reconfiguration module 264 is implemented to configurevarious resources within the server blade chassis, such as switchresources and storage resources. Accordingly, configure switchsub-module 266 and configure storage sub-module 268 may effect portionsof various policies during their execution. The functionality ofconfiguration module 264, as well as configure switch sub-module 266 andconfigure storage sub-module 268 will be further described as varioussteps in the execution of blade-specific policies is later illustrated.

Compatibility matrix module 270 is responsible for the implementationand maintenance of a compatibility matrix. The compatibility matrixdescribes compatibility relationships between server blade chassisresources. For example, a compatibility matrix, or a portion thereof,may be consulted to determine if a selected blade is compatible with aspecified scheme or regime (e.g., sparing of certain volumes).

Sparing module 272 executes sparing policies, such as volume and bladesparing policies for a selected server blade within the server bladechassis. As with the various additional sub-modules described above,additional functionality with respect to the implementation of suchsparing policies will be described below.

Turning to FIG. 3, an exemplary method 274 for implementing andcontrolling a number of blade-specific policies within a server bladechassis is depicted. Method 274 begins (step 276) by defining a numberof policies for execution on the server blade chassis in view of aparticular implementation (step 278). In the depicted embodiment, a slotpolicy 280, a blade policy 282, a BIOS policy 284, an application policy286, a volume sparing policy 288, a blade sparing policy 290, and an OSpolicy 292 are all defined. Again, however, the number of policies mayvary depending on a particular situation.

Each of the various policies may be defined and initialized by thepolicy controller module. With respect to each of the various policies,a number of routines, subroutines, and the like, may be defined (step294). For example, for a particular blade policy, a routine whichexecutes upon the insertion of a blade into the server blade chassis, orblade insertion routine, may be defined. In another example, for aparticular blade sparing policy, a routine which executes upon thedetected failure of a selected server blade in the server blade chassis,or blade failure routine, may be defined.

A number of rules relevant to the execution of one or more policies mayalso be defined (step 296). The rules may relate to the order thatparticular steps in a particular policy are executed, for example. Therules may relate to the order that policies themselves are executedrelative to additional policies or additional routines.

Once the number of policies, routines, and rules have been initializedand defined, the policy controller module may execute a first routine ofa first policy, in view of the rules relevant to the execution of thatpolicy (step 298). Policy controller module coordinates the execution ofthe first policy with the execution of a routine of a second policy, inview of applicable rules, and the first policy (step 300). Thecoordination of the execution of various policies may also depend on avariety of factors, such as time, usage, predetermined triggermechanisms, customer input, external factors, and the like.

The policy controller module, depending on the situation, may execute anumber of policies within a particular server blade chassis. Executionof these policies may be coordinated, one with another, until thevarious policies have been executed, and routines associated with thepolicies have been completed. The policy controller module may utilize avariety of information, including that obtained internal to the advancedmanagement module, and elsewhere, to perform this coordinationfunctionality. The policy controller module may coordinate onboardfunctionality with other subcomponents of the advanced managementmodule, including various sub-modules or it may coordinate with othercomponents within and/or without the server blade chassis. Once thecoordination functionality has concluded, the method 274 then ends (step302).

FIGS. 4-7, following, illustrate steps of various exemplary policiesthat feature and incorporate policy-based dynamic mapping functionalityof resources within a server blade chassis. Such dynamic mappingfunctionality is made possible by such sub-modules as the informationmanager module 260, configuration modules 264, 266, and 268, andcompatibility matrix module 270 (FIG. 2) in communication with othervarious sub-modules, and as coordinated by the policy controller module.The dynamic mapping functionality may incorporate one or more mapsdescribing a relationship between two or more of the server bladechassis resources. The map may be maintained in the information managermodule 260, or elsewhere.

As one skilled in the art will appreciate, various steps in thefollowing methodologies may be implemented in differing ways to suit aparticular application. In addition, the described methodologies may beimplemented by various means, such as hardware, software, firmware, or acombination thereof operational on or otherwise associated with theserver blade environment. For example, the mechanisms depicted in thefollowing FIGS. 4-13 may be implemented, partially or wholly, as acomputer program product including a computer-readable storage mediumhaving computer-readable program code portions stored therein. Thecomputer-readable storage medium may include disk drives, flash memory,digital versatile disks (DVDs), compact disks (CDs), and other types ofstorage mediums.

FIG. 4 illustrates an exemplary pre-insertion application routine 304 ofan exemplary slot policy. Prior to the insertion of a server blade in aselected slot of the server blade chassis, the policy controller modulemay complete the exemplary routine with the assistance of the variouscontributing sub-modules. As a first step, the routine 304 begins (step306) with one or more slot-to-volume maps being initialized (step 308).Each of the slot-to-volume maps describe a relationship between a slotof the server blade chassis and a volume assigned to the slot.

As a next step, the configure switch module is called to complete thezoning setup requirements for an associated switch (step 310). The BIOSmodule is employed to make relevant BIOS assignments based on theslot-to-volume maps that were initialized (step 312). The configurestorage module is called to allocate boot and data volumes for theselected slot if the boot and data volumes are determined to be notpresent (step 314). The OS repository module is called to set up an OSon the boot volume, again if the boot volume is determined to be notpresent (step 316). The selected slot is assigned to the volume(s) perthe slot-to-volume mappings (step 318). The routine 304 then ends (step320).

FIG. 5 illustrates an exemplary blade insertion routine 322 of theexemplary slot policy first described in FIG. 4. The policy controllermodule, or a subcomponent, may observe that a blade has been inserted ina selected slot as a predetermined trigger mechanism. In response, themethod 322 begins (step 324) by the information manager module queryingthe inserted blade for relevant information (step 326). This informationmay include, for instance, information such as vital product data (VPD)(including part numbers, serial numbers, and engineering change levelsfrom either the Customized VPD object class or platform specific areas),compatibility information, application information, and so forth. Forexample, the routine may gather VPD from the inserted blade into theselected slot.

Based on the collected information, the compatibility matrix module isqueried to obtain a compatibility relationship for the inserted blade inthe selected slot (step 328). The inserted blade's BIOS is programmed toboot from the pre-mapped volume (based on the slot-to-volume map(s))using the remote BIOS interface sub-module (step 330). If compatibilitychecks return without error, and the BIOS information is satisfactorilyprogrammed, then the blade is powered on (step 332). The routine 322then ends (step 334).

The methodology described in FIG. 5 illustrates an exemplary embodimentof slot policy functionality that, pursuant to a predetermined trigger(in this case, a blade insertion) reconfigures at least one of theresources of the server blade chassis. Throughout the followingexemplary methodologies, it may be seen that a variety of server bladechassis resources may be similarly reconfigured pursuant to theexecution of a particular policy or routine.

FIG. 6 illustrates an exemplary blade insertion routine 336 of anexemplary blade policy. Routine 336 begins (step 338) with a query, inresponse to a detection of the blade insertion, to the informationmanager module for specific information of the inserted server blade(step 340). A blade-to-volume map, maintained on the information managermodule, is queried to determine which associated volume is required forthe inserted server blade (step 342). If the inserted server blade is anew blade, then the configuration module functionality is implicated(step 344). Accordingly, the OS repository is called to obtain theblade's respective OS (step 346). The BIOS module is called to obtainthe blade's BIOS based on a blade-to-BIOS mapping (step 348). Assumingthe boot and data volumes are not present (due to a new blade), theconfigure storage module is called to allocate boot and data volumes forthe particular slot (step 350). The OS repository is again called to setup the OS on the boot volume (step 352).

To perform appropriate zoning setup for an associated switch, theconfigure switch module is called (step 354). The blade-to-volumemapping returned from the information manager module is assigned to theinserted blade (step 356). The BIOS module is called, and the insertedblade's BIOS is programmed to boot from the mapped volume using theremote BIOS interface (step 358). Finally, the blade is powered on (step360). Routine 336 then ends (step 362).

FIG. 7 illustrates an exemplary removal routine 364 of an exemplaryblade policy. Routine 364 begins (step 366) with the detection of ablade removal from the server blade chassis. Following the detection ofa blade removal, the switch is unconfigured in that the switch cannotaccess the previously assigned volume (step 368). The routine 364 thenends (step 370).

FIGS. 8-13, following, illustrate various routines for implementingexemplary sparing policies. Portions of the following methodologies mayinvolve configuring a resource operational on the server blade chassisas a spare resource, configuring the sparing policy for the spareresource; and in response to observing a predetermined trigger for thespare resource, executing the sparing policy for the spare resource. Thesparing policy executed, for example, may be a blade sparing policy or avolume sparing policy. The spare resource may be configured as such forat least one of a number of server blades.

An operating relationship between the spare resource and the number ofserver blades, such as a one-to-one relationship, a one-to-manyrelationship, and a many-to-many relationship may be configured. Theoperating relationship may be based on a machine signature of the serverblade, or based on a slot location in the server blade chassis.

Here, as before, one of a variety of predetermined trigger mechanismsmay cause the execution of various policies and/or routines associatedwith those policies. For example, one predetermined trigger may be thedetection of a selected server blade inserted in the server bladechassis. Once the insertion is detected, a sparing policy may beexecuted which, if the selected server blade is validated as a spareresource, may include maintaining the selected server blade in astandby, powered-off state.

In another example, a volume sparing policy may be defined to beexecuted following the detection of a volume failure. A first volume maybe configured as a primary resource, and a second volume may beconfigured as a spare resource. Subsequent to detecting a volumefailure, a zoning change on a switch associated with the first andsecond volumes may be requested. A basic input output system (BIOS)associated with the first and second volumes may be updated with acorrect boot location. The BIOS update may be facilitated by a basemanagement controller (BMC). A server blade associated with the secondvolume may be then powered on, and the second volume may be booted from.

FIG. 8 illustrates an exemplary power-on routine 372 for an exemplaryblade sparing policy. Routine 372 begins (step 374) by initializing ablade sparing table (step 376). The blade sparing table may bemaintained on the information manager module, or elsewhere within theadvanced management module. The blade sparing table may identify, forexample, server blades designated as spares and additional server bladesdesignated as live.

For each blade in the server blade chassis, the information managermodule may be consulted to obtain crucial information required toperform various sparing operations (step 378). The configuration modulemay then be called (step 380). The configuration module may use the BIOSmodule to configure active blades to boot from correct volumes (step382). The associated switch is then zoned such that active blades mayaccess the appropriate volume (step 384). As a next step, all activeblades are powered on (step 386). Server blades designated as spareresources are not powered on. The compatibility matrix is queried forall spare server blades (step 388). Those spare blades which are notcompatible are then removed from the blade sparing table. Routine 372then ends (step 390).

FIG. 9 illustrates an exemplary blade insertion routine 392 for anexemplary blade sparing policy. Routine 392 begins (step 394) with aquery to a user to determine if the user wishes a selected server bladeto be a live or a spare resource (step 396). If the user designates theserver blade as a spare, the user is again asked to specify the bladefor confirmation. The routine 392 then checks the spare forcompatibility (again using the compatibility matrix), and the spare isadded to the blade sparing table (step 398). The spare is not powered on(Step 400). Routine 392 then ends (step 402).

FIG. 10 illustrates an exemplary blade failure routine 404 for anexemplary blade sparing policy. In response to the detection of a bladehardware failure, routine 404 begins (step 406) by querying the bladesparing table to determine which spare to use (step 408). Theconfiguration module functionality is again implicated, and theconfiguration module is called (step 410). Using the configure switchmodule, the volume is zoned in order for the spare to “see” the device(step 412).

As a next step, the BIOS module is used to configure the spare serverblade to boot from the newly zoned volume (step 414). The blade ispowered on (step 416). The sparing module is called to reconfigurealternate spares to the new active blade (step 418). The routine 404then ends (step 420).

FIG. 11 illustrates an exemplary blade removal routine 422 for anexemplary blade sparing policy. In response to the detection of a bladeremoval, routine 422 begins (step 424) by the sparing module beingcalled to reconfigure alternate spares (since the instant blade is nolonger accessible) (step 426). The routine 422 then ends (step 428).

FIG. 12 illustrates an exemplary power-on routine 430 for an exemplaryvolume sparing policy. Routine 430 begins (step 432) at power on to callthe sparing module to initialize a volume sparing table (step 434). Thevolume sparing table functions similarly to the blade sparing table, inthat particular volumes may be identified as designated spare or livevolumes, for example. The volume sparing table may be maintained on theinformation manager module, on the sparing module, or elsewhere.

Once the volume sparing table is initialized, the information managermodule may be consulted for each blade in the server blade chassis togather critical system information, such as VPD (step 436). Theconfiguration module functionality is implicated (step 438), and theBIOS module is used in conjunction with the configuration module toconfigure blades to boot from designated active volumes (step 440). Theconfigure switch module is used to zone the associated switch (step442). Using the configure storage module, volume mirroring may beenabled via the application module in order for all active and inactivevolumes contain the same data (step 444). The blades are all powered on(step 446). The routine 430 then ends (step 448).

FIG. 13 illustrates an exemplary volume failure routine 450 for anexemplary volume sparing policy. Upon a detection of a volume failure,routine 450 begins (step 452) by querying the volume sparing tableinitialized during the execution of the power-on routine (step 454) todetermine which spare volume to use. The spare volume is zoned using theconfigure switch module in order for the selected server blade to seethe volume (step 456). Using the BIOS module, the blade is configured toboot from the newly zoned volume (step 458). As a next step, the bladepower is recycled (step 460). The routine 450 then ends (step 462).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention. Thus,appearances of the phrases “in one embodiment,” “in an embodiment,” andsimilar language throughout this specification may, but do notnecessarily, all refer to the same embodiment.

Some of the functional units described in this specification have beenlabeled as modules in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom VLSI circuits or gate arrays,off-the-shelf semiconductors such as logic chips, transistors, or otherdiscrete components. A module may also be implemented in programmablehardware devices such as field programmable gate arrays, programmablearray logic, programmable logic devices, or the like.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of executable code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.

While one or more embodiments of the present invention have beenillustrated in detail, the skilled artisan will appreciate thatmodifications and adaptations to those embodiments may be made withoutdeparting from the scope of the present invention as set forth in thefollowing claims.

1. A method for implementing and controlling a plurality ofserver-specific policies for a plurality of blade servers by amanagement module in communication with the plurality of blade servers,comprising: defining a first policy of a plurality of policies for eachof the plurality of blade servers; managing a plurality of rulesrelevant to an execution of the first policy; and coordinating theexecution of the first policy with an execution of a second policy ofthe plurality of policies, including coordinating the execution of aBIOS policy according to a blade insertion routine, the BIOS policyapplying at least one blade-specific BIOS setting to one of theplurality of blade servers upon the insertion of the one of theplurality of blade servers into a blade server chassis.
 2. The method ofclaim 1, wherein coordinating the execution of the first policy with theexecution of the second policy includes assigning at least one of theplurality of rules with the first policy to a portion of the managementmodule for execution.
 3. The method of claim 1, wherein defining thefirst policy of the plurality of policies for each of the plurality ofblade servers includes configuring a policy controller moduleoperational on the management module for controlling execution of theplurality of policies.
 4. The method of claim 1, wherein coordinatingthe execution of the first policy with the execution of the secondpolicy of the plurality of policies includes coordinating the executionof one of a slot policy, a blade policy, a blade sparing policy, avolume sparing policy, an operating system policy, and an applicationpolicy with the second policy.
 5. The method of claim 1, whereindefining the first policy of the plurality of policies for each of theplurality of blade servers includes defining a plurality of routines forthe first policy.
 6. The method of claim 5, wherein defining theplurality of routines includes defining the blade server insertionroutine for the first policy executed upon an insertion of the one ofthe plurality of blade servers into the blade server chassis.
 7. Themethod of claim 5, wherein defining the plurality of routines includesdefining a failure routine for the first policy executed upon a failureof a blade server component.
 8. A system for implementing andcontrolling a plurality of server-specific policies for a plurality ofblade servers using a management module in communication with theplurality of blade servers, comprising: a policy controller moduleoperational on the management module, wherein the policy controllermodule is adapted for: defining a first policy of a plurality ofpolicies for each of the plurality of blade servers, managing aplurality of rules relevant to an execution of the first policy, andcoordinating the execution of the first policy with an execution of asecond policy of the plurality of policies, including coordinating theexecution of a BIOS policy according to a blade insertion routine, theBIOS policy applying at least one blade-specific BIOS setting to one ofthe plurality of blade servers upon the insertion of the one of theplurality of blade servers into a blade server chassis.
 9. The system ofclaim 8, wherein the policy controller module is further adapted forassigning at least one of the plurality of rules with the first policyto a portion of the management module for execution.
 10. The system ofclaim 8, further including: an operating system repository module incommunication with the policy controller module for implementing anoperating system policy assigned by the policy controller module, aninformation manager module in communication with the policy controllermodule for managing information within the management module, and a BIOSmodule in communication with the policy controller module forimplementing the BIOS policy assigned by the policy controller module.11. The system of claim 8, further including: a configuration module incommunication with the policy controller module for configuring a serverresource per the first policy, a compatibility matrix module incommunication with the policy controller module for determining acompatibility of a server resource per the first policy, and a sparingmodule in communication with the policy controller module forimplementing a sparing policy assigned by the policy controller module.12. The system of claim 8, further including an application module incommunication with the policy controller module for executing apolicy-specific application.
 13. The system of claim 8, wherein thepolicy controller module is further adapted for defining a plurality ofroutines for the first policy.
 14. The system of claim 13, wherein theplurality of routines includes the blade server insertion routineexecuted upon an insertion of the one of the plurality of blade serversinto the blade server chassis, and a failure routine executed upon afailure of a blade server component.
 15. A computer program product forimplementing and controlling a plurality of server-specific policies ofa plurality of blade servers by a management module in communicationwith the plurality of blade servers, the computer program productcomprising a computer-readable storage medium having computer-readableprogram code portions stored therein, the computer-readable program codeportions comprising: a first executable portion for defining a firstpolicy of a plurality of policies for each of the plurality of bladeservers; a second executable portion for managing a plurality of rulesrelevant to an execution of the first policy; and a third executableportion for coordinating the execution of the first policy with anexecution of a second policy of the plurality of policies, includingcoordinating the execution of a BIOS policy according to a bladeinsertion routine, the BIOS policy applying at least one blade-specificBIOS setting to one of the plurality of blade servers upon the insertionof the one of the plurality of blade servers into a blade serverchassis.
 16. The computer program product of claim 15, wherein the thirdexecutable portion for coordinating the execution of the first policywith the execution of the second policy includes a fifth executableportion for assigning at least one of the plurality of rules with thefirst policy to a portion of the management module for execution. 17.The computer program product of claim 15, wherein the first executableportion for defining the first policy of a plurality of policies foreach of the plurality of blade servers includes a fifth executableportion for configuring a policy controller module operational on themanagement module for controlling execution of the plurality ofpolicies.
 18. The computer program product of claim 15, wherein thethird executable portion for coordinating the execution of the firstpolicy with the execution of the second policy of the plurality ofpolicies includes a fifth executable portion for coordinating theexecution of one of a slot policy, a blade policy, a blade sparingpolicy, a volume sparing policy, an operating system policy, and anapplication policy with the second policy.
 19. The computer programproduct of claim 15, wherein the first executable portion for definingthe first policy of the plurality of policies for each of the pluralityof blade servers includes a fifth executable portion for defining aplurality of routines for the first policy.
 20. The computer programproduct of claim 19, wherein the fifth executable portion for definingthe plurality of routines includes a sixth executable portion fordefining the blade server insertion routine for the first policyexecuted upon an insertion of one of the plurality of blade servers intothe blade server chassis and a sixth executable portion for defining afailure routine for the first policy executed upon a failure of a bladeserver component.